Learning Objectives

After completing this lesson, you’ll be able to:

What is a Null Value?

Null values are an important part of FME’s attribute handling. Not every dataset has null values, and not every format supports them; but when they do exist, it is important for FME to handle them correctly.

In general, a null attribute value is the equivalent of nothing. However, it’s important to be precise in our terminology because there are many ways to represent nothing, for example:

In fact, Safe Software’s developers identified fifteen (15) different ways for “nothing” to be represented in spatial and tabular data!

So when we talk about null, it has a particular meaning. For us, null is a specific state that is deliberately set to signify that the information does not exist. It tells us that the lack of information is not a mistake, as a missing or empty value might be.

Because there are so many different methods, this section will discuss ways to handle "nothing" attribute values, but with a particular emphasis on null values.

Note

FME's three main definitions are null, empty, and missing. To clarify with an analogy, let's consider the kitchen of your house.

Suppose there is no sink, there is no place to put a sink, and there is no plumbing for the sink. The builder foolishly decided there would be no sink, so the sink is missing.

If there was a place for the sink, and plumbing for the sink, but the sink was not there, then it would be null. The builder set aside space for the sink, but hasn't added it yet.

If there is a sink, but there is no water in it, then the sink exists, but it is empty.

How Does FME Represent Nothing?

FME’s internal engine has its own state to represent null. However, when presented to the user, a null value is usually represented as <null>.

For example, this feature in the Logger has <null> for the ParkName attribute:

Null value in the Translation Log

Similarly, the FME Data Inspector will depict nulls as <null>:

Missing and null values in the Visual Preview Table view

Notice how we have a wide range of "nothing" values here. The ParkName is a true <null>, the RefParkId has a value of -9999, and Washrooms is <missing> (meaning the entire attribute doesn't exist).

Note

<missing> is an interesting concept. You might be asking, "how do we know when an attribute is missing?" But a better question is "how do we know that the attribute should exist?"

Using our previous analogy, we know the kitchen sink is missing because the house blueprints specified a sink. The sink should be there, but it isn't.

In FME we know an attribute should exist because it appears in the reader schema. For example, in the above screenshot, Washrooms appears in the schema, but for some reason, certain features do not have that attribute. That makes the attribute <missing> from those features.